<rss version="2.0" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
    <channel>
        <title>Business Analyst Community &amp; Resources | Modern Analyst</title> 
        <link>https://modernanalyst.com</link> 
        <description>RSS feeds for Business Analyst Community &amp; Resources | Modern Analyst</description> 
        <ttl>60</ttl> <item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6675/Happy-Alternate-and-Exception-Paths-are-Applicable-to-More-Than-Just-Use-Cases.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6675</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6675&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Happy, Alternate, and Exception Paths are Applicable to More Than Just Use Cases</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6675/Happy-Alternate-and-Exception-Paths-are-Applicable-to-More-Than-Just-Use-Cases.aspx</link> 
    <description>The concepts of Happy, Alternate, and Exception Paths originated with Use Cases, but turn out to be applicable to any graphical modelling technique that depicts Flow. This article presents examples of Business Process, Activity, and State Transition diagrams with these concepts represented simply using the common &amp;ldquo;Traffic Light&amp;rdquo; colors green, amber, and red. The benefits to both business analysts and stakeholders are discussed.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 03 Feb 2025 03:05:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6675</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6489/Use-Cases-The-Business-Analysts-Best-Friend.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6489</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6489&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Use Cases: The Business Analyst’s Best Friend</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6489/Use-Cases-The-Business-Analysts-Best-Friend.aspx</link> 
    <description>I like use cases. There, I said it, and I&amp;rsquo;m not sorry. Use cases have fallen out of fashion in recent years, being largely replaced by user stories on agile projects. The two techniques can coexist and complement each other, however.&amp;nbsp;&amp;nbsp;Use cases offer several advantages that user stories lack. This article describes some of the many benefits that use cases can provide and why every business analyst (BA), product owner (PO), and software development team should include them in their tool kit.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 02 Sep 2024 06:53:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6489</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6490/When-Use-Cases-Arent-Enough-Event-Analysis.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6490</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6490&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>When Use Cases Aren’t Enough: Event Analysis</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6490/When-Use-Cases-Arent-Enough-Event-Analysis.aspx</link> 
    <description>Although use cases are valuable for many projects, sometimes event analysis is a more effective requirements elicitation technique. Valuable as they are, use cases aren&amp;rsquo;t the ideal tool for every type of product. A complementary requirements elicitation strategy is to explore the various events that a system or product could experience and how it should respond to each of them. The response depends on what state the system is in when it detects the event. Event analysis is particularly well-suited for middleware products and real-time systems that include both software and hardware components.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 21 Apr 2024 21:12:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6490</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6093/User-Stories-vs-Use-Cases.aspx#Comments</comments> 
    <slash:comments>5</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6093</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6093&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>User Stories vs Use Cases</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6093/User-Stories-vs-Use-Cases.aspx</link> 
    <description>What is Use Case?

Use case represents requirement in the form of user interactions with the system. Use case is always written with a specific user goal in mind. Each use case must contain an actor and verb. For example, &amp;lsquo;online buyer&amp;rsquo; is an actor and &amp;lsquo;add item to cart&amp;rsquo; is a verb.

A use case diagram represents the scope of all the features of the solution. It follows Unified Modelling Language&amp;trade; notation. Use case diagram comprises of several use cases that make the system altogether.

What is User Story?

User story is a business analysis artifact that is also user or persona driven. It describes the business need in the form of an ability user (or system) wants in the solution. It also must state why the ability is required and what the benefits of that ability are. It does not have any mandatory format though

User story is part of the (product/project) backlog. The backlog in turn contains user stories/tasks (requirements) in a linear fashion. Backlog is usually prioritized from high to low, additionally with a ranking when priorities are the same. When it is prioritized by business value of the tasks/stories in it, it is called managed backlog. In many projects, user stories are also represented visually as a user story map, which is a structured visualization of a backlog. User story map is a map of user stories that are transposed from a linear backlog, onto a visual working board.

Each of this concept is a detailed topic in itself. For the context of this article, I will limit it only at the introductory level. Let&amp;#39;s now look into differences and similarities between user stories and use cases.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 07 Aug 2022 08:37:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6093</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5874/Models-And-Diagrams-What-Is-The-Difference.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5874</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5874&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Models And Diagrams – What Is The Difference?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5874/Models-And-Diagrams-What-Is-The-Difference.aspx</link> 
    <description>A diagram is a 2-dimensional representation of a story, which shows elements and their relationships on a single canvas. An element is shown on a single diagram. (To show the same element information on a 2 diagrams, the element is duplicated.) When the properties of a diagram element are changed, the change is reflected only on that diagram.

A model is a 3-dimensional representation of a collection of related stories, which captures diagram elements as model components. A component includes all element properties and relationships between different elements on all diagrams. A single model component can be shown as elements on several diagrams. A change to the properties of a diagram element or model component is reflected on every diagram where that component is displayed.

A model does not necessarily need to include any diagrams. Diagramming is the most common method for creating and maintaining model components, but the diagrams can be deleted without changing the model.

If a picture is worth a thousand words, then a diagram converts those words into a story. A model organizes those stories into a book.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 05 Jul 2021 17:54:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5874</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5720/Handling-CRUD-in-your-Use-Cases.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5720</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5720&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Handling C.R.U.D. in your Use Cases</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5720/Handling-CRUD-in-your-Use-Cases.aspx</link> 
    <description>So how do you handle CRUD in your use cases? Please don&amp;rsquo;t confuse CRUD with CRAP in your use cases. That&amp;rsquo;s a lot harder to deal with and requires a conversation with your subject matter experts (SMEs).&amp;nbsp;CRUD is an acronym for Create, Read, Update and Delete. It describes the lifecycle in the maintenance of system data, whether that data is stored in a database or is file based data stored in a document management system like SharePoint.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 08 Nov 2020 05:24:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5720</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5585/Use-Cases--The-New-School.aspx#Comments</comments> 
    <slash:comments>5</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5585</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5585&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Use Cases - The New School</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5585/Use-Cases--The-New-School.aspx</link> 
    <description>In the world of software development Use Cases are one of many very powerful techniques often used these days.&amp;nbsp; Use cases describe how a person or a system interacts with the solution being modeled/built to achieve a goal. Basically, it&amp;rsquo;s a step by step explanation of what a user can do and how the solution must respond.
As any other business analysis technique, use cases have their advantages and disadvantages. One of the main disadvantages of use cases is that this technique is not graphical &amp;ndash; a use case diagram is but use case descriptions are not, and use case descriptions really lack of visualization&amp;nbsp;especially if there are multiple alternative flows and exception flows that branch out and then loop back into the main one.</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 20 Apr 2020 02:03:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5585</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5438/Why-Modeling-Is-an-Essential-Business-Analysis-Technique.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5438</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5438&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Why Modeling Is an Essential Business Analysis Technique</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5438/Why-Modeling-Is-an-Essential-Business-Analysis-Technique.aspx</link> 
    <description>Visual analysis models provide a powerful set of tools that let business analysts depict system information at various levels of abstraction. These models serve as an aid to understanding, as well as an aid to communicating. Alas, I fear that modeling is somewhat of a neglected practice. I believe modeling is an essential skill every BA should master. Here&amp;rsquo;s why.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 22 Mar 2020 14:27:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5438</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5465/Generalization-Specialization-Use-Case-Diagrams-and-Scenarios.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5465</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5465&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Generalization / Specialization Use Case  Diagrams and Scenarios</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5465/Generalization-Specialization-Use-Case-Diagrams-and-Scenarios.aspx</link> 
    <description>Several years ago I was looking for examples using the generalization / specialization technique with use cases. They are not easier to find. And they are typically limited to a use case diagram like the two below. This article provides examples of both the diagrams and the scenarios for a future gas station business.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 05 Jan 2020 20:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5465</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5347/Requirements-In-Context-Part-3-Scope-High-Level-Requirements.aspx#Comments</comments> 
    <slash:comments>3</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5347</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5347&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Requirements In Context Part 3: Scope = High-Level Requirements</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5347/Requirements-In-Context-Part-3-Scope-High-Level-Requirements.aspx</link> 
    <description>
Project Scope.&amp;nbsp;We will see how scope&amp;nbsp;statements, when making reference to&amp;nbsp;business functionality, lead directly to&amp;nbsp;High-Level&amp;nbsp;requirements.&amp;nbsp; Gathering requirements for a business information system is&amp;nbsp;most often&amp;nbsp;done within the context of a project.&amp;nbsp;Approval of a project&amp;nbsp;includes its&amp;nbsp;sponsors&amp;nbsp;signing off&amp;nbsp;on its scope.&amp;nbsp;The&amp;nbsp;scope&amp;nbsp;for a business information system project is&amp;nbsp;typically&amp;nbsp;defined in&amp;nbsp;functional&amp;nbsp;terms.&amp;nbsp;Items in scope make reference to (or should make reference to)&amp;nbsp;business functions, processes and/or activities&amp;nbsp;that are to be delivered.

</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 05 May 2019 20:46:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5347</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5247/7-Powerful-Analysis-Techniques-to-Boost-Value-from-Your-Models.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5247</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5247&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>7 Powerful Analysis Techniques to Boost  Value from Your Models</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5247/7-Powerful-Analysis-Techniques-to-Boost-Value-from-Your-Models.aspx</link> 
    <description>Strategists, architects, process experts, software developers, data managers and other professionals involved in changing the enterprise often put substantial effort in creating all kinds of useful models of their designs. In many cases, such business models, enterprise architecture models, business process models, software models, or data models are only used to specify some design, i.e. to describe what should be built.&amp;nbsp;
But there is much more value to be had from these models, by using powerful analysis techniques to elicit new insights. In the following pages I will cover 7 of these analyses, discussing the business outcomes you can achieve with their help.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 13 Jan 2019 19:30:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5247</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3681/Deep-Dive-Models-in-Agile-Series-State-Models.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3681</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3681&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Deep Dive Models in Agile Series: State Models</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3681/Deep-Dive-Models-in-Agile-Series-State-Models.aspx</link> 
    <description>State Models include two RML Data models (State Tables and State Diagrams) that show the transition of an object through various states or statuses, including which transitions are valid and what triggers an object to transition state. A state is a short-form description of a stage in a data object&amp;rsquo;s life that influences the behavior of the system.


These two models are covered together in this paper because they generally show the same information, just in different ways. These models are great for any object which has state about which there might be business rules, like workflow processes!</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 08 May 2017 01:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3681</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2020/End-to-End-UML-Case-Study-for-a-Stock-Broker.aspx#Comments</comments> 
    <slash:comments>3</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2020</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2020&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>End-to-End UML Case Study for a Stock Broker</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2020/End-to-End-UML-Case-Study-for-a-Stock-Broker.aspx</link> 
    <description>The problem with many Unified Modeling Language (UML) educational texts is that they present the various concepts each in isolation; so you see a use case diagram for one problem domain, a class diagram for an entirely different problem domain, and you never get to see the important traceability between the diagrams.
In this case study we aim to put it right by working through a single problem from use cases and activity diagrams, through sequence diagrams and state diagrams, to class diagrams and component diagrams. We have arranged the case study as three distinct perspectives or aspects as follows.</description> 
    <dc:creator>speeditonline</dc:creator> 
    <pubDate>Sun, 07 Aug 2016 23:27:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2020</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2013/End-to-End-UML-Component-Diagram-and-Deployment-Diagram.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2013</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2013&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>End-to-End UML: Component Diagram and Deployment Diagram</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2013/End-to-End-UML-Component-Diagram-and-Deployment-Diagram.aspx</link> 
    <description>The UML Component Diagram along with the complementary UML Deployment Diagram shows how a software solution will be delivered and deployed in the form of interconnected components that interoperate via well-defined interfaces. You can think of this as analogous to how electronic components are wired together, and in this context you should consider that any one component may be replaced by a different but compatible component with no adverse effect.
</description> 
    <dc:creator>speeditonline</dc:creator> 
    <pubDate>Mon, 21 Sep 2015 04:15:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2013</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2021/End-to-End-UML-State-Diagram.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2021</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2021&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>End-to-End UML: State Diagram</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2021/End-to-End-UML-State-Diagram.aspx</link> 
    <description>The UML State Diagram, sometimes known as the Statechart Diagram or Static Transition Diagram, defines the entire lifecycle of a business entity or object in terms of the messages it receives and the responses it makes from the moment of creation until the moment of destruction.</description> 
    <dc:creator>speeditonline</dc:creator> 
    <pubDate>Mon, 29 Jun 2015 08:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2021</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2016/End-to-End-UML-Use-Case-Specification.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2016</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2016&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>End-to-End UML: Use Case Specification</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2016/End-to-End-UML-Use-Case-Specification.aspx</link> 
    <description>A UML Use Case is an atomic system function with a well-defined and standardized&amp;nbsp;specification, which is performed by or o behalf of a system user or &amp;lsquo;actor&amp;rsquo;. This article describes how a UML Use Case Specification should be written.
</description> 
    <dc:creator>speeditonline</dc:creator> 
    <pubDate>Mon, 25 May 2015 13:40:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2016</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3116/Use-Case-Fragments.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3116</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3116&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Use Case Fragments</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3116/Use-Case-Fragments.aspx</link> 
    <description>A typical business function might contain several unique events each of which we want to end up as a component of a larger software application.  So how do we go from a table containing textual information to a specification which a developer can use?</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Fri, 14 Nov 2014 08:08:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3116</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2952/Anatomy-of-a-Use-Case-Skip-the-Outline-and-Dive-into-the-Main-Scenario.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2952</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2952&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Anatomy of a Use Case: Skip the Outline and Dive into the Main Scenario</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2952/Anatomy-of-a-Use-Case-Skip-the-Outline-and-Dive-into-the-Main-Scenario.aspx</link> 
    <description>This article discusses Stephen King&amp;rsquo;s creative writing method and provides an example of using it in developing a use case narrative: the main scenario with alternate and exception paths.  Yes, that is correct &amp;ndash; Stephen King, the prolific writer of contemporary horror, science fiction and fantasy novels.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 26 Oct 2014 11:31:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2952</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2010/End-to-End-UML-Class-Diagram.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2010</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2010&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>End-to-End UML: Class Diagram</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2010/End-to-End-UML-Class-Diagram.aspx</link> 
    <description>The UML Class Diagram, sometimes known as the Static Structure Diagram, shows the dependencies and persistent associations between object classes.
</description> 
    <dc:creator>speeditonline</dc:creator> 
    <pubDate>Sun, 19 Oct 2014 21:40:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2010</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2018/End-to-End-UML-Sequence-Diagram.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2018</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2018&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>End-to-End UML: Sequence Diagram</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2018/End-to-End-UML-Sequence-Diagram.aspx</link> 
    <description>A UML Sequence Diagram is used most commonly to show the realization of a use case in terms of interactions between business entities or software objects. This diagram therefore helps with the transition from non-object oriented activity diagrams and use case diagrams to the object-oriented paradigm of modern software development.</description> 
    <dc:creator>speeditonline</dc:creator> 
    <pubDate>Mon, 13 Oct 2014 09:44:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2018</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1252/Complete-Business-Systems-Analysis-Model-UML-Example.aspx#Comments</comments> 
    <slash:comments>5</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1252</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1252&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Complete Business-Systems Analysis Model (UML Example)</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1252/Complete-Business-Systems-Analysis-Model-UML-Example.aspx</link> 
    <description>This is a complete example of a Business/Systems Analysis Model using UML and including: Use Cases, Activity Diagrams, Context Diagram, and more.</description> 
    <dc:creator>baldrick</dc:creator> 
    <pubDate>Thu, 21 Aug 2014 13:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1252</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2835/Why-Dont-Use-Cases-Just-Go-Away.aspx#Comments</comments> 
    <slash:comments>22</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2835</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2835&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Why Don’t Use Cases Just Go Away?!</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2835/Why-Dont-Use-Cases-Just-Go-Away.aspx</link> 
    <description>Use case models have been around for decades. Long after Information Engineering was all the rage and through object-oriented analysis and design they hung around. They threatened to disappear when Agile methods gained popularity, but here they are. Discussed, dissected, blogged about—why don’t they just go away?!&amp;#160;</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 20 Jan 2014 03:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2835</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2017/End-to-End-UML-Use-Case-Diagram.aspx#Comments</comments> 
    <slash:comments>4</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2017</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2017&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>End-to-End UML: Use Case Diagram</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2017/End-to-End-UML-Use-Case-Diagram.aspx</link> 
    <description>Use case diagrams are used to show the decomposition of a business problem or software solution into a set of discrete functions (the use cases) which can be enacted by or on behalf of users (the actors). In a nutshell, this diagram shows who (the actors) can do what (the use cases) when interacting with the software solution.
</description> 
    <dc:creator>speeditonline</dc:creator> 
    <pubDate>Sun, 04 Aug 2013 22:25:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2017</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2011/End-to-End-UML-Activity-Diagram.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2011</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2011&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>End-to-End UML: Activity Diagram</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2011/End-to-End-UML-Activity-Diagram.aspx</link> 
    <description>Unified Modeling Language (UML) Activity Diagrams are rather like traditional flowcharts that may be used to describe the steps required to enact high level business processes or low level algorithms. From the software analyst’s perspective these diagrams are most useful for representing business processes, so this will be our focus here. Whereas activity diagrams are often relegated to the final chapters of the UML text books, I prefer to present them up-front as the logical starting point for any UML analysis and design endeavor.</description> 
    <dc:creator>speeditonline</dc:creator> 
    <pubDate>Mon, 15 Jul 2013 06:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2011</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2368/Bridging-the-Gap-between-Business-and-Software-Architectures.aspx#Comments</comments> 
    <slash:comments>3</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2368</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2368&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Bridging the Gap between Business and Software Architectures</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2368/Bridging-the-Gap-between-Business-and-Software-Architectures.aspx</link> 
    <description>We are frequently asked about connecting and tracing software architecture elements to business processes by integrating BPMN business models and software models in UML (Unified Modeling Language)...&amp;nbsp;Now we will explore how to supplement business architecture with software architecture.&amp;nbsp;
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 01 Oct 2012 00:30:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2368</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2145/BA-ABCs-C-is-for-Class-Diagram.aspx#Comments</comments> 
    <slash:comments>10</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2145</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2145&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>BA ABCs: “C” is for Class Diagram</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2145/BA-ABCs-C-is-for-Class-Diagram.aspx</link> 
    <description>Today&amp;rsquo;s letter is &amp;ldquo;C&amp;rdquo; &amp;ndash; for Class Diagrams. Business Analysts use Class Diagrams to help them discover &amp;lsquo;structural&amp;rsquo; business rules and to document them in a visual form that is readily understood by developers.&amp;nbsp; What is a structural rule?
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 13 Feb 2012 09:32:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2145</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2071/Document-Decisions-Separately-and-Explicitly-A-Proposed-Use-Case-Scenario-Best-Practice.aspx#Comments</comments> 
    <slash:comments>9</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2071</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2071&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Document Decisions Separately and Explicitly – A Proposed Use Case Scenario Best Practice</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2071/Document-Decisions-Separately-and-Explicitly-A-Proposed-Use-Case-Scenario-Best-Practice.aspx</link> 
    <description>This article proposes a use case best practice technique: Always document decisions separately and explicitly in use case scenarios. This practice assists the business analyst in identifying where alternate and exception paths may be needed.This is similar to how decisions and resulting gateways are documented in Business Process Model and Notation (BPMN).</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Tue, 17 Jan 2012 10:47:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2071</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2111/Data-Modelling-Object-Oriented-Development.aspx#Comments</comments> 
    <slash:comments>4</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=2111</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=2111&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Data Modelling &amp; Object Oriented Development</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/2111/Data-Modelling-Object-Oriented-Development.aspx</link> 
    <description>At some stage in their working life, every business analyst will have some involvement with data modelling. They may need to model how data is (or will be) used or - if they only deal with requirements investigation - then someone else in the team will need to verify that the data to support new functions will be available.</description> 
    <dc:creator>pddean</dc:creator> 
    <pubDate>Mon, 19 Dec 2011 05:23:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:2111</guid> 
    <enclosure url="https://modernanalyst.com:443/Portals/0/Public%20Uploads%203/Data_Modelling_and_Object_Oriented_Development.pdf" length="467770" type="application/pdf" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1905/Use-Case-Points-an-analysis-phase-estimating-technique.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1905</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1905&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Use Case Points: an analysis phase estimating technique</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1905/Use-Case-Points-an-analysis-phase-estimating-technique.aspx</link> 
    <description>Use Case Points are used as an analysis phase technique for estimating software development. Assuming the Business Analyst (BA) composes system use cases for describing functional requirements, the BA can use this technique for estimating the follow-on implementation effort. This article reviews the process of estimating the follow-on development effort for use cases.
</description> 
    <dc:creator>speeditonline</dc:creator> 
    <pubDate>Mon, 01 Aug 2011 04:03:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1905</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1868/An-Introduction-to-Swimlane-Diagrams.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1868</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1868&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>An Introduction to Swimlane Diagrams</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1868/An-Introduction-to-Swimlane-Diagrams.aspx</link> 
    <description>A swimlane diagram is a type of process flow diagram (also sometimes called a cross-functional diagram) that features divisions or &amp;quot;lanes.&amp;quot; Each lane is assigned an actor (which may be an individual, department, division, group, machine, entity, and so on), or even a phase or stage in a process, that is responsible for the activity or work described in the lane.
</description> 
    <dc:creator>speeditonline</dc:creator> 
    <pubDate>Mon, 27 Jun 2011 07:25:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1868</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1830/An-Introduction-to-Activity-Diagrams.aspx#Comments</comments> 
    <slash:comments>6</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1830</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1830&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>An Introduction to Activity Diagrams</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1830/An-Introduction-to-Activity-Diagrams.aspx</link> 
    <description>An activity diagram is a type of flowchart that is part of the UML (Unified Modeling Language) standard. Its purpose is to enable analysts to present a concrete, easy-to-follow visual of the workflow of a business use case.
</description> 
    <dc:creator>speeditonline</dc:creator> 
    <pubDate>Mon, 02 May 2011 10:37:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1830</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1556/How-the-BA-Can-Take-Advantage-of-Free-Online-Diagramming-Tools.aspx#Comments</comments> 
    <slash:comments>5</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1556</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1556&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>How the BA Can Take Advantage of Free Online Diagramming Tools</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1556/How-the-BA-Can-Take-Advantage-of-Free-Online-Diagramming-Tools.aspx</link> 
    <description>Almost every business analyst uses diagramming software in their arsenal of analysis tools. According to BABOK 2.0, an analyst’s traditional purpose in using diagramming tools is to “support the rapid drawing and documentation of a model, typically by providing a set of templates for a particular notation which are used to develop diagrams based on it.” Diagrams not only make requirements clearer to stakeholders through modeling, they help clarify an analyst’s thinking on a project through the process of their very creation.</description> 
    <dc:creator>speeditonline</dc:creator> 
    <pubDate>Sun, 07 Nov 2010 10:33:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1556</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1531/How-Static-Modeling-Skills-Can-Improve-Your-Performance-as-a-Business-Analyst.aspx#Comments</comments> 
    <slash:comments>9</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1531</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1531&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>How Static Modeling Skills Can Improve Your Performance as a Business Analyst</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1531/How-Static-Modeling-Skills-Can-Improve-Your-Performance-as-a-Business-Analyst.aspx</link> 
    <description>While most business analyst roles don&#39;t explicitly require static modeling expertise, developing a better understanding of static modeling concepts can be a measurable forward step for business analysts seeking to develop new competencies. Such skills can be useful in many aspects of the BA work, from obtaining a better understanding of stakeholders&#39; information needs, to documenting those needs in unambiguous ways and communicating them more effectively to the technical team.</description> 
    <dc:creator>speeditonline</dc:creator> 
    <pubDate>Mon, 18 Oct 2010 05:55:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1531</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1500/From-Research-to-Implementation-Activity-Diagram-Usage-and-Benefits.aspx#Comments</comments> 
    <slash:comments>10</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1500</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1500&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>From Research to Implementation: Activity Diagram – Usage and Benefits</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1500/From-Research-to-Implementation-Activity-Diagram-Usage-and-Benefits.aspx</link> 
    <description>As part of the Unified Modeling Language, Activity diagrams are often utilized for many software projects. However, a few questions about Activity diagrams linger in the minds of many Business Analysts, such as: Who is really using them?&amp;#160;What kind of projects are they being used on?&amp;#160;Why are people not using them?&amp;#160;How are people using them?&amp;#160;Are they providing any benefit?
&amp;#160;</description> 
    <dc:creator>speeditonline</dc:creator> 
    <pubDate>Mon, 27 Sep 2010 04:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1500</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1442/Use-Cases-and-Business-Rules-Can-They-Work-Together.aspx#Comments</comments> 
    <slash:comments>28</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1442</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1442&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Use Cases and Business Rules: Can They Work Together?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1442/Use-Cases-and-Business-Rules-Can-They-Work-Together.aspx</link> 
    <description>There is much written today about separating business rules from other dimensions of automated business systems. Without proper separation, they operate in enterprises without a great deal of thought given to them. Ironically, they may be the most important dimension because they represent important business thinking behind processes, use cases, for example.&amp;nbsp;This article discusses various approaches for dealing with business rules and use cases.
&amp;nbsp;</description> 
    <dc:creator>speeditonline</dc:creator> 
    <pubDate>Mon, 09 Aug 2010 04:48:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1442</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1217/From-Research-to-Implementation-Use-Case-Diagrams-Usage-and-Benefits.aspx#Comments</comments> 
    <slash:comments>10</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=1217</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=1217&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>From Research to Implementation: Use Case Diagrams – Usage and Benefits</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/1217/From-Research-to-Implementation-Use-Case-Diagrams-Usage-and-Benefits.aspx</link> 
    <description>Some people use them. Some people don&#39;t use them. Some people create them using sophisticated tools. Some use basic drawing programs. As part of the Unified Modeling Language, Use Case diagrams are often the starting point for many software projects. However, questions about Use Case diagrams still linger in the minds of many Business Analysts...</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 04 Jan 2010 05:23:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:1217</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/620/UML--Business-Context.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=620</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=620&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>UML - Business Context</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/620/UML--Business-Context.aspx</link> 
    <description>“Where does UML fit?” is a common question among new (and not so new!) business analysts. We all know that the M stands for modelling but beyond this, perceptions start to differ. In its current form (V2.0) UML consists of 13 diagram types all of which provide a different view of a system. 

In this article we’ll take a brief look at which of the 13 diagrams are of most relevance for us and how they fit together...
Author: Jan Kusiak</description> 
    <dc:creator>pddean</dc:creator> 
    <pubDate>Tue, 02 Dec 2008 02:04:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:620</guid> 
    <enclosure url="https://modernanalyst.com:443/Portals/0/Public%20Uploads/UML_Business_Context.pdf" length="238092" type="application/pdf" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/592/Stakeholder-Communications--Pictures-not-Words.aspx#Comments</comments> 
    <slash:comments>5</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=592</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=592&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Stakeholder Communications - Pictures not Words</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/592/Stakeholder-Communications--Pictures-not-Words.aspx</link> 
    <description>Many people on our Business Analysis workshop ask why we use dataflow diagrams (DFDs). Why not Use Case…or even BPMN? After all DFDs have been around for 20 years, surely the world has moved on?
Well, has it? The primary purpose of a business analyst is to communicate – to stakeholders and to solution providers – and when it comes to communication we all know that pictures (diagrams) are much more effective and less ambiguous than words. Remember the phrase &quot;A picture is worth a thousand words&quot;. The question is – which type of diagram best suits our needs? In this article, written by IRM&#39;s Training Services Manager Jan Kusiak, we’ll look at using diagrams for stakeholder communications.

Author: Jan Kusiak
</description> 
    <dc:creator>pddean</dc:creator> 
    <pubDate>Sat, 01 Nov 2008 00:37:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:592</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/353/Enterprise-Architect-for-Business-Analysts.aspx#Comments</comments> 
    <slash:comments>7</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=353</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=353&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Enterprise Architect for Business Analysts</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/353/Enterprise-Architect-for-Business-Analysts.aspx</link> 
    <description>As a software architect and developer I&amp;rsquo;ve used Enterprise Architect (EA) from Sparx Systems (www.sparxsystems.com) for a number of years. In that time I&amp;rsquo;ve spent considerable time and energy trying to get our business analysts to do the same. While I&amp;rsquo;ve had some success I must admit it&amp;rsquo;s been an uphill battle. I suspect this is partly because EA is often seen as a technical person&amp;rsquo;s tool. And that&amp;rsquo;s not altogether surprising.


 Enterprise Architect &amp;ndash; the name itself is completely misleading. EA is not only for people with the title &amp;lsquo;Enterprise Architect&amp;rsquo;. It&amp;rsquo;s for the entire project team, from BA&amp;rsquo;s to Testers and even for Clients. 
 User Interface &amp;ndash; for developers the user interface of EA is extremely familiar and intuitive. It looks like a lot of the tools they use already. For non-technical users more familiar with tools like Microsoft Office it is somewhat more intimidating. 


So, if you&amp;rsquo;re a Business Analyst looking for a tool that can help you do your job more effectively then read on.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Tue, 06 May 2008 04:35:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:353</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/254/UML-2-Class-Diagram-Guidelines.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=254</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=254&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>UML 2 Class Diagram Guidelines</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/254/UML-2-Class-Diagram-Guidelines.aspx</link> 
    <description>UML class diagrams show the classes of the system, their inter-relationships, and the operations and attributes of the classes. Class diagrams are typically used, although not all at once, to:

    Explore domain concepts in the form of a domain model
    Analyze requirements in the form of a conceptual/analysis model
    Depict the detailed design of object-oriented or object-based software

A class model is comprised of one or more class diagrams and the supporting specifications that describe model elements including classes, relationships between classes, and interfaces. There are guidelines for:

    General issues
    Classes
    Interfaces
    Relationships
    Inheritance
    Aggregation and Composition

Author: Scott W. Ambler</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 10 Feb 2008 06:40:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:254</guid> 
    <enclosure url="http://www.agilemodeling.com/style/classDiagram.htm" length="-1" type="text/html; charset=UTF-8" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/253/UML-2-Class-Diagrams.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=253</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=253&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>UML 2 Class Diagrams</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/253/UML-2-Class-Diagrams.aspx</link> 
    <description>UML 2 class diagrams are the mainstay of object-oriented analysis and design. UML 2 class diagrams show the classes of the system, their interrelationships (including inheritance, aggregation, and association), and the operations and attributes of the classes. Class diagrams are used for a wide variety of purposes, including both conceptual/domain modeling and detailed design modeling. Although I prefer to create class diagrams on whiteboards because simple tools are more inclusive most of the diagrams that I’ll show in this article are drawn using a software-based drawing tool so you may see the exact notation.
In this article I discuss:

    Conceptual class diagrams
    Design class diagrams
    How to create UML class diagrams
    Suggested reading

Author: Scott W. Ambler</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 10 Feb 2008 06:36:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:253</guid> 
    <enclosure url="http://www.agilemodeling.com/artifacts/classDiagram.htm" length="-1" type="text/html; charset=UTF-8" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/252/UML-basics-The-class-diagram.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=252</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=252&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>UML basics: The class diagram</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/252/UML-basics-The-class-diagram.aspx</link> 
    <description>Structure diagrams in general
Structure diagrams show the static structure of the system being modeled. focusing on the elements of a system, irrespective of time. Static structure is conveyed by showing the types and their instances in the system. Besides showing system types and their instances, structure diagrams also show at least some of the relationships among and between these elements and potentially even show their internal structure. 

Structure diagrams are useful throughout the software lifecycle for a variety of team members. In general, these diagrams allow for design validation and design communication between individuals and teams. For example, business analysts can use class or object diagrams to model a business&#39;s current assets and resources, such as account ledgers, products, or geographic hierarchy. Architects can use the component and deployment diagrams to test/verify that their design is sound. Developers can use class diagrams to design and document the system&#39;s coded (or soon-to-be-coded) classes. 

The class diagram in particular
UML 2 considers structure diagrams as a classification; there is no diagram itself called a &quot;Structure Diagram.&quot; However, the class diagram offers a prime example of the structure diagram type, and provides us with an initial set of notation elements that all other structure diagrams use. And because the class diagram is so foundational, the remainder of this article will focus on the class diagram&#39;s notation set. By the end of this article you should have an understanding of how to draw a UML 2 class diagram and have a solid footing for understanding other structure diagrams.
Author: Donald Bell</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Thu, 10 Jan 2008 06:28:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:252</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/123/The-Pros-and-Cons-of-Use-Case-Diagrams.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=123</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=123&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Pros and Cons of Use Case Diagrams</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/123/The-Pros-and-Cons-of-Use-Case-Diagrams.aspx</link> 
    <description>
In the Unified Modeling Language (UML), use cases are visually represented as ellipses. However, in spite of its popularity and size, UML has little of practical use to offer modelers beyond this simple iconic representation. Trying to capture and present requirements using just use case diagrams can often render the otherwise useful technique of use cases almost useless.
Practitioners are often drawn to expressing their intent by overworking the limited use case diagram notation, losing readers in a myriad of bubbles muddled together with obscure relationships and microscopic text. This article takes a step back to examine the pitfalls and recommend a more balanced and restrained approach.

Author: Kevlin Henney</description> 
    <dc:creator>cadams5</dc:creator> 
    <pubDate>Sat, 29 Sep 2007 17:46:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:123</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7/Analysis-and-Design-Considered-Harmful.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=7</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=7&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>&quot;Analysis and Design&quot; Considered Harmful</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7/Analysis-and-Design-Considered-Harmful.aspx</link> 
    <description>This article describes a common pitfall of thinking of analysis and design together as a single process, and highlights the need to treat analysis and design as two separate processes. The author, points out that much of the UML standard, as it is explained today, is described in terms of design artifacts rather than analysis artifacts.
Author: Conrad Weisert</description> 
    <dc:creator>cadams5</dc:creator> 
    <pubDate>Wed, 01 Aug 2007 17:14:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:7</guid> 
    <enclosure url="http://www.idinews.com/analysisDesign.html" length="114" type="text/html" />
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3/Alternatives-of-Alternatives.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Alternatives of Alternatives</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3/Alternatives-of-Alternatives.aspx</link> 
    <description>Geri Schneider Winters writes about&amp;nbsp;whether or not&amp;nbsp;you could write alternatives to alternatives in use cases. 
There is no actual standard for the formatting of a use case specification, just guidelines and best practices.&amp;nbsp; Therefore, if using alternatives to alternatives in use cases makes the use case more clear - use it, by any means.
Author: Geri Schneider Winters</description> 
    <dc:creator>admin</dc:creator> 
    <pubDate>Tue, 17 Jul 2007 03:32:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/67/Database-Modelling-in-UML.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=67</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=67&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Database Modelling in UML</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/67/Database-Modelling-in-UML.aspx</link> 
    <description>When it comes to providing reliable, flexible and efficient object persistence for software systems, today&#39;s designers and architects are faced with many choices. From the technological perspective, the choice is usually between pure Object-Oriented, Object-Relational hybrids, pure Relational and custom solutions based on open or proprietary file formats (eg. XML, OLE structured storage). From the vendor aspect Oracle, IBM, Microsoft, POET and others offer similar but often-incompatible solutions.
This article is about only one of those choices, that is the layering of an object-oriented class model on top of a purely relational database. This is not to imply this is the only, best or simplest solution, but pragmatically it is one of the most common, and one that has the potential for the most misuse.
We will begin with a quick tour of the two design domains we are trying to bridge: firstly the object-oriented class model as represented in the UML, and secondly the relational database model.
For each domain we look only at the main features that will affect our task. We will then look at the techniques and issues involved in mapping from the class model to the database model, including object persistence, object behaviour, relationships between objects and object identity. We will conclude with a review of the UML Data Profile (as proposed by Rational Software).
Some familiarity with object-oriented design, UML and relational database modelling is assumed.
Author: Geoffrey Sparks</description> 
    <dc:creator>admin</dc:creator> 
    <pubDate>Thu, 05 Jul 2007 21:32:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:67</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/10/Using-UML-Activity-Diagrams-for-the-Process-View.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=10</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=10&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Using UML Activity Diagrams for the Process View</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/10/Using-UML-Activity-Diagrams-for-the-Process-View.aspx</link> 
    <description>In this article, the focus shifts to a particular view in the 4+1 Architecture Views, defined by the Rational Unified Process. We will examine how to use Activity Diagrams as &quot;roadmaps&quot; for the Process View, to capture processing flows as a series of steps. We will also discuss several techniques for creating these diagrams and ensuring their effectiveness.
Author: Ben Lieberman</description> 
    <dc:creator>host</dc:creator> 
    <pubDate>Tue, 01 May 2007 17:54:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:10</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/8/UML-Activity-Diagrams-Versatile-Roadmaps-for-Understanding-System-Behavior.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=8</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=8&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>UML Activity Diagrams: Versatile Roadmaps for Understanding System Behavior</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/8/UML-Activity-Diagrams-Versatile-Roadmaps-for-Understanding-System-Behavior.aspx</link> 
    <description>The core purpose of software development is to provide solutions to customers&#39; real problems. Use cases are a vital aspect of a technique that has been used successfully to ensure that development projects actually focus on these problems. They are used to discover, capture, and present customer requirements in a form that is accessible to developers, testers, and other stakeholders in a development project. To detail a use case, it is critical to capture basic, alternate, and exceptional flows of execution, which represent major and minor threads of execution the system encounters as it processes customer requests.
Using the &quot;standard&quot; use-case form, these flows can be captured using plain English to describe sequential activities. These descriptions are quite detailed, however, and they can be difficult to decipher -- especially within a complex set of use-case scenarios.
This article describes another way to capture these flows: by using Unified Modeling Language (UML) Activity Diagrams that depict the flows as &quot;roadmaps&quot; of system functional behavior. These roadmaps are analogous to AAA (Automobile Association of America) roadmaps, in that they show what routes you can take but do not indicate whether you will take them.
An AAA map, moreover, supplies only enough information to identify locations of interest, leaving detailed descriptions of the road for companion travel guides. Similarly, Activity Diagrams show a comprehensive summary of use-case flows but leave the design details up to other artifacts.
We will also take a brief look at other ways to use Activity Diagrams during the development lifecycle.
Author: Ben Lieberman</description> 
    <dc:creator>host</dc:creator> 
    <pubDate>Tue, 01 May 2007 17:46:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:8</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6/UML-Activity-Diagrams-Detailing-User-Interface-Navigation.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>UML Activity Diagrams: Detailing User Interface Navigation</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6/UML-Activity-Diagrams-Detailing-User-Interface-Navigation.aspx</link> 
    <description>The author illustrates how to use UML Activity Diagrams to capture and communicate the details of user interface navigation and functionality, and explain three stereotypes: presentation, exception, and connector. 
Author: Ben Lieberman</description> 
    <dc:creator>host</dc:creator> 
    <pubDate>Tue, 01 May 2007 17:05:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/68/The-Use-Case-Model.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=68</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=68&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Use Case Model</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/68/The-Use-Case-Model.aspx</link> 
    <description>The Use Case Model describes the proposed functionality of the new system. A Use Case represents a discrete unit of interaction between a user (human or machine) and the system. A Use Case is a single unit of meaningful work; for example login to system, register with system and create order are all Use Cases. Each Use Case has a description which describes the functionality that will be built in the proposed system. A Use Case may &#39;include&#39; another Use Case&#39;s functionality or &#39;extend&#39; another Use Case with its own behaviour.
Author: Sparx Systems</description> 
    <dc:creator>admin</dc:creator> 
    <pubDate>Tue, 17 Apr 2007 21:35:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:68</guid> 
    
</item>

    </channel>
</rss>